Method and apparatus for protecting moderator access for a conference call

ABSTRACT

A method for protecting moderator access using a communication device. The method includes: displaying an interface for editing a conference call profile, the conference call profile including conference call scheduling information including one or more addressees for communicating with a conference call server, wherein the conference call scheduling information further includes a moderator access code and a participant access code; generating an indicator for the conference call profile for excluding sending of the moderator access code to invited participants; and storing the conference call profile including the indicator in a memory of the communication device. A communication device can be configured to perform the method.

RELATED APPLICATION

This application claims priority from U.S. Provisional PatentApplication 61/454,315 titled, “Method for Protecting Moderator Accessfor a Conference Call,” filed Mar. 18, 2011, and is hereby incorporatedby reference in its entirety.

TECHNICAL FIELD

Example embodiments relate to conference call systems and methods, forexample for protecting moderator access for a conference call.

BACKGROUND

During a conference call, voice or media connections are typically madebetween two or more communication devices such as telephones or mobilephones.

When scheduling a conventional conference call, a user typically isrequired to configure the conference call manually. For example, allconference call information can be entered into specific fields or tags,including the time, attendees, host, and conference access number. Whena quick meeting needs to be convened, there is time overhead required toset up the meeting. In addition, the user can be distracted from thesubstantive content of the meeting in order to facilitate theadministrative aspect in coordinating the meeting.

One difficulty with existing conferencing systems is that unauthorizedparticipants can attempt to join a conference call. The participants ofa conference call are sometimes loosely defined wherein originalinvitees can forward invitations and access codes to others who can thenparticipate. With only rudimentary security procedures such as aconference call dial-in number and access code almost anyone from anylocation can access a conference call, which could compromise security.

Other difficulties with existing teleconferencing systems will beapparent to those skilled in the art in view of the detailed descriptionbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made, by way of example, to the accompanyingdrawings which show example embodiments, and in which:

FIG. 1 shows, in block diagram form, an example system for managingenterprise-related mobile calls, including an enterprise communicationsplatform, to which example embodiments can be applied;

FIG. 2 shows, in block diagram form, further details of an embodiment ofthe enterprise communications platform;

FIG. 3 shows another embodiment of the enterprise communicationsplatform;

FIG. 4 shows yet another embodiment of the enterprise communicationsplatform;

FIG. 5 shows further details of the enterprise communications platformof FIG. 3;

FIG. 6 shows, in block diagram form, a conference call system includingthe enterprise communications platform shown in FIG. 1 and clientdevices;

FIG. 7 shows a block diagram illustrating a mobile communication devicein accordance with an example embodiment;

FIG. 8 shows an example flow diagram of a method for protectingmoderator access in accordance with an example embodiment;

FIG. 9 shows a user interface as displayed on a mobile communicationdevice, for scheduling of a calendar meeting for a conference call, inaccordance with an example embodiment;

FIG. 10 shows an example user interface for creating a conference callprofile, in accordance with an example embodiment;

FIG. 11 shows the example user interface of FIG. 10 in anotheroperation;

FIG. 12A shows an example user interface for configuring conference callscheduling information, in accordance with an example embodiment;

FIG. 12B shows the example user interface of FIG. 10A in anotheroperation;

FIG. 12C shows the example user interface of FIG. 10A in anotheroperation;

FIG. 13 shows an example user interface for displaying a receivedinvitation message on a mobile communication device, in accordance withan example embodiment;

FIG. 14 shows an example user interface for configuring conference callscheduling information from the received invitation message, inaccordance with an example embodiment; and

FIG. 15 shows a reminder interface for a scheduled conference callsession, in accordance with an example embodiment.

Similar reference numerals can be used in different figures to denotesimilar components.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Some example embodiments generally relate to protecting moderator accessfor a conference call.

Some example embodiments generally relate to creating and editingconference profiles. The profiles feature can provide meeting organizersthe option to save conference information into profiles. When creatingmeetings using the conference call application, the host organizers canreadily populate the conference information for the meeting by selectinga profile for that meeting. The necessary details will be automaticallyinserted into the meeting invitation.

In some example embodiments, the profiles can include an indicator forexcluding sending of moderation information, such as a moderator accesscode, to invited participants.

In one example embodiment, there is provided a method for protectingmoderator access using a communication device. The method includes:displaying an interface for editing a conference call profile, theconference call profile including conference call scheduling informationincluding one or more addressees for communicating with a conferencecall server, wherein the conference call scheduling information furtherincludes a moderator access code and a participant access code;generating an indicator for the conference call profile for excludingsending of the moderator access code to invited participants; andstoring the conference call profile including the indicator in a memoryof the communication device.

In another example embodiment, there is provided a non-transitorycomputer readable medium having recorded thereon statements andinstructions for execution by one or more devices for protectingmoderator access for a conference call, the statements and instructionscomprising code means for performing the method.

In yet another example embodiment, there is provided a communicationdevice including: a controller; a communications subsystem; a memory;and a display for displaying an interface for editing a conference callprofile, the conference call profile including conference callscheduling information including one or more addressees forcommunicating with a conference call server, wherein the conference callscheduling information further includes a moderator access code and aparticipant access code. The controller is configured for: generating anindicator for the conference call profile for excluding sending of themoderator access code to invited participants, and storing theconference call profile including the indicator in the memory.

In yet another example embodiment, there is provided a method forcreating a conference call profile from a communication device, whereinthe communication includes a memory for storing an event record. Themethod includes: identifying from the event record one or moreaddressees for communicating with a conference call server; generating aconference call profile having one or more address fields and populatingthe address fields with the addresses; and storing the conference callprofile in the memory.

Example embodiments relate to the control and management of conferencecall communications. Although reference is made to “calls” and “talk” inthe description of example embodiments below, it will be appreciatedthat some of the described systems and methods can be applicable tosession-based communications in general and not limited to voice calls.Reference to calls can, for example, include shared data (e.g.presentation content) as well as media sessions which can, for example,include video and/or audio. The various communications can include bothsynchronous and asynchronous communications to implement such “calls”.

Reference is now made to FIG. 1, which shows, in block diagram form, anexample system, generally designated 10, for the control and managementof communications. The system 10 includes an enterprise or businesssystem 20, which in many embodiments includes a local area network(LAN). In the description below, the enterprise or business system 20can be referred to as an enterprise network 20. It will be appreciatedthat the enterprise network 20 can include more than one network and canbe located in multiple geographic areas in some embodiments.

The enterprise network 20 can be operatively connected, often through afirewall 22, to a wide area network (WAN) 30, such as the Internet. Theenterprise network 20 can also be operatively connected to a publicswitched telephone network (PSTN) 40 via direct inward dialing (DID)trunks or primary rate interface (PRI) trunks.

The enterprise network 20 can also communicate with a public land mobilenetwork (PLMN) 50, which can also be referred to as a wireless wide areanetwork (WWAN) or, in some cases, a cellular network. The operativeconnection with the PLMN 50 can be made via a relay 26, as understood inthe art.

The enterprise network 20 can also provide a wireless local area network(WLAN) 32 a featuring wireless access points. Other WLANs 32 can existoutside the enterprise network 20. For example, WLAN 32 b can beoperatively connected to WAN 30.

The system 10 can include a number of enterprise-associated mobiledevices 11 (only one shown). The mobile devices 11 can include devicesequipped with communications modules for cellular communication throughthe PLMN 50, mobile devices equipped for Wi-Fi communications over oneof the WLANs 32, or dual-mode devices capable of both cellular and datacommunications. WLANs 32 can be configured in accordance with one of theIEEE 802.11 specifications.

It will be understood by a person with ordinary skill in the art thatthe mobile devices 11 include one or more radio transceivers andassociated processing hardware and software to enable wirelesscommunications with the PLMN 50 and/or one of the WLANs 32. In variousembodiments, the PLMN 50 and mobile devices 11 can be configured tooperate in compliance with any one or more of a number of wirelessprotocols, including GSM, GPRS, CDMA, EDGE, UMTS, EvDO, HSPA, 3GPP, or avariety of others. It will be appreciated that the mobile device 11 canroam within the PLMN 50 and across PLMNs, in a known manner, as the usermoves. In some instances, the dual-mode mobile devices 11 and/or theenterprise network 20 are configured to facilitate roaming between thePLMN 50 and a WLAN 32, and are thus capable of seamlessly transferringsessions (such as voice calls) from an operative connection with thecellular interface of the dual-mode device 11 to the WLAN 32 interfaceof the dual-mode device 11, and vice versa.

The mobile devices 11 can consist of various types of communicationdevices. Such mobile devices 11 can include “Class A” devices, which areable to function continuously as dual-mode devices, capable of bothmedia and data communications. Mobile devices 11 can also include“non-Class A” devices, which can function as dual-mode devices forinitialization or prior to an operative connection with the enterprisecommunications platform 14, but can lose data functionality once a mediasession (e.g., voice call) is established. The enterprise network 20 canalso include additional client devices which are voice-only ormedia-only devices, which can be digital or analog for communicationwith the PSTN or PLMN, and which need not have data capabilities (hereinreferred to as “voice-only” or “media-only” devices). In otherembodiments, the mobile devices 11 can include any suitable clientdevice configured with the communications functionality describedherein, and can, for example, include computer devices, relays, proxies,gateways and any appropriate User Agents (as defined in SIP).

The enterprise network 20 typically includes a number of networkedservers, computers, and other devices. For example, the enterprisenetwork 20 can operatively connect one or more desktop or laptopcomputers 15 (one shown). The operative connection can be wired orwireless in some embodiments. The enterprise network 20 can alsooperatively connect to one or more digital telephone sets 17 (oneshown).

The enterprise network 20 can include one or more mail servers, such asmail server 24, for coordinating the transmission, storage, and receiptof electronic messages for client devices operating within theenterprise network 20. Typical mail servers include the MicrosoftExchange Server™ and the IBM Lotus Domino™ server. Each user within theenterprise typically has at least one user account within the enterprisenetwork 20. Associated with each user account is message addressinformation, such as an e-mail address. Messages addressed to a usermessage address are stored on the enterprise network 20 in the mailserver 24. The messages can be retrieved by the user using a messagingapplication, such as an e-mail client application. The messagingapplication can be operating on a user's computer 15 operativelyconnected to the enterprise network 20 within the enterprise. In someembodiments, the user can be permitted to access stored messages using aremote computer, for example at another location via the WAN 30 using aVPN connection. Using the messaging application, the user can alsocompose and send messages addressed to others, within or outside theenterprise network 20. The messaging application causes the mail server24 to send a composed message to the addressee, often via the WAN 30.

The relay 26 serves to route messages received over the PLMN 50 from themobile device 11 to the corresponding enterprise network 20. The relay26 also pushes messages from the enterprise network 20 to the mobiledevice 11 via the PLMN 50.

The enterprise network 20 also includes an enterprise server 12.Generally, the enterprise server 12 is configured to collectively servethe needs of the enterprise network 20, for example to provide and/orsynchronize messaging, contacts and calendaring information betweenservers, desktop workstations 15, and mobile devices 11. Together withthe relay 26, the enterprise server 12 functions to redirect or relayincoming e-mail messages addressed to a user's e-mail address within theenterprise network 20 to the user's mobile device 11 and to relayincoming e-mail messages composed and sent via the mobile device 11 outto the intended recipients within the WAN 30 or elsewhere. Theenterprise server 12 and relay 26 together facilitate “push” e-mailservice for the mobile device 11 enabling the user to send and receivee-mail messages using the mobile device 11 as though the user wereoperatively connected to an e-mail client within the enterprise network20 using the user's enterprise-related e-mail address, for example oncomputer 15.

As is typical in many enterprises, the enterprise network 20 includes aPrivate Branch eXchange (although in various embodiments the PBX can bea standard PBX or an IP-PBX, for simplicity the description below usesthe term PBX to refer to both) 16 having an operative connection withthe PSTN 40 for routing incoming and outgoing voice calls for theenterprise. The PBX 16 is operatively connected to the PSTN 40 via DIDtrunks or PRI trunks, for example. The PBX 16 can use ISDN signalingprotocols for setting up and tearing down circuit-switched connectionsthrough the PSTN 40 and related signaling and communications. In someembodiments, the PBX 16 can be operatively connected to one or moreconventional analog telephones 19. The PBX 16 is also operativelyconnected to the enterprise network 20 and, through it, to telephoneterminal devices, such as digital telephone sets 17, softphonesoperating on computers 15, etc. Within the enterprise, each individualcan have an associated extension number, sometimes referred to as a PNP(private numbering plan), or direct dial phone number. Calls outgoingfrom the PBX 16 to the PSTN 40 or incoming from the PSTN 40 to the PBX16 are typically circuit-switched calls. Within the enterprise, e.g.between the PBX 16 and terminal devices, voice calls are oftenpacket-switched calls, for example Voice-over-IP (VoIP) calls.

The enterprise network 20 can further include a Service ManagementPlatform (SMP) 18 for performing some aspects of messaging or sessioncontrol, like call control and advanced call processing features. TheSMP 18 can, in some cases, also perform some media handling.Collectively the SMP 18 and PBX 16 can be referred to as the enterprisecommunications platform, generally designated 14. It will be appreciatedthat the enterprise communications platform 14 and, in particular, theSMP 18, is implemented on one or more servers having suitablecommunications interfaces for operatively connecting to andcommunicating with the PBX 16 and/or DID/PRI trunks. Although the SMP 18can be implemented on a stand-alone server, it will be appreciated thatit can be implemented into an existing control agent/server as a logicalsoftware component. As will be described below, the SMP 18 can beimplemented as a multi-layer platform.

The enterprise communications platform 14 implements the switching tooperatively connect session legs and can provide the conversion between,for example, a circuit-switched call and a VoIP call, or to operativelyconnect legs of other media sessions. In some embodiments, in thecontext of voice calls the enterprise communications platform 14provides a number of additional functions including automated attendant,interactive voice response (IVR), call forwarding, voice mail, etc. Itcan also implement certain usage restrictions on enterprise users, suchas blocking international calls or 1-900 calls. In many embodiments,Session Initiation Protocol (SIP) can be used to set-up, manage, andterminate media sessions for voice calls. Other protocols can also beemployed by the enterprise communications platform 14, for example, WebServices, Computer Telephony Integration (CTI) protocol, SessionInitiation Protocol for Instant Messaging and Presence LeveragingExtensions (SIMPLE), and various custom Application ProgrammingInterfaces (APIs), as will be described in greater detail below.

One of the functions of the enterprise communications platform 14 is toextend the features of enterprise telephony to the mobile devices 11.For example, the enterprise communications platform 14 can allow themobile device 11 to perform functions akin to those normally availableon a standard office telephone, such as the digital telephone set 17 oranalog telephone set 15. Example features can include direct extensiondialing, enterprise voice mail, conferencing, call transfer, call park,etc.

Reference is now made to FIGS. 2 to 4, which show example embodiments ofthe enterprise communications system 14. FIG. 2 illustrates anembodiment intended for use in a circuit-switched TDM context. The PBX16 is coupled to the SMP 18 via PRI operative connection 60 or othersuitable digital trunk. In some embodiments, the PRI operativeconnection 60 can include a first PRI operative connection, a second PRIoperative connection, and a channel service unit (CSU), wherein the CSUis a mechanism for operatively connecting computing devices to digitalmediums in a manner that allows for the retiming and regeneration ofincoming signals. It will be appreciated that there can be additional oralternative operative connections between the PBX 16 and the SMP 18.

In this embodiment, the SMP 18 assumes control over both call processingand the media itself. This architecture can be referred to as “FirstParty Call Control”. Many of the media handling functions normallyimplemented by the PBX 16 are handled by the SMP 18 in thisarchitecture. Incoming calls addressed to any extension or direct dialnumber within the enterprise, for example, are always first routed tothe SMP 18. Thereafter, a call leg is established from the SMP 18 to thecalled party within the enterprise, and the two legs are bridged.Accordingly, the SMP 18 includes a digital trunk interface 62 and adigital signal processing (DSP) conferencing bridge 64. The DSPconferencing bridge 64 performs the bridging of calls for implementationof various call features, such as conferencing, call transfer, etc. Thedigital trunk interface 62 can be implemented as a plurality oftelephonic cards, e.g. Intel Dialogic cards, interoperatively connectedby a bus and operating under the control of a processor. The digitaltrunk interface 62 can also be partly implemented using a processormodule such as, for example, a Host Media Processing (HMP) processor.

The SMP 18 can include various scripts 66 for managing call processing.The scripts 66 are implemented as software modules, routines, functions,etc., stored in non-volatile memory and executed by the processor of theSMP 18. The scripts 66 can implement call flow logic, business logic,user preferences, call service processes, and various featureapplications.

FIG. 3 shows another embodiment in which the PBX 16 performs thefunctions of terminating and/or bridging media streams, but call controlfunctions are largely handled by the SMP 18. In this embodiment, the SMP18 can be referred to as a call control server 18. This architecture canbe referred to as “Third-Party Call Control”.

The call control server 18 is coupled to the PBX 16, for example throughthe LAN, enabling packet-based communications and, more specifically,IP-based communications. In one embodiment, communications between thePBX 16 and the call control server 18 are carried out in accordance withSIP. In other words, the call control server 18 uses SIP-basedcommunications to manage the set up, tear down, and control of mediahandled by the PBX 16. In one example embodiment, the call controlserver 18 can employ a communications protocol conforming to theECMA-269 or ECMA-323 standards for Computer Supported TelecommunicationsApplications (CSTA).

FIG. 4 shows yet another embodiment of the enterprise communicationssystem 14. This embodiment reflects the adaptation of an existing set ofcall processing scripts to an architecture that relies on third-partycall control, with separate call control and media handling. The SMP 18includes a call processing server 74. The call processing server 74includes the scripts or other programming constructs for performing callhandling functions. The SMP 18 also includes a SIP server 72 and a mediaserver 76. The separate SIP server 72 and media server 76 logicallyseparate the call control from media handling. The SIP server 72interacts with the call processing server 74 using acomputer-implemented communications handling protocol, such as one ofthe ECMA-269 or ECMA-323 standards. These standards prescribe XML basedmessaging for implementing Computer Supported TelecommunicationsApplications (CSTA).

The SIP server 72 interacts with the media server 76 using SIP-basedmedia handling commands. For example, the SIP server 72 and media server76 can communicate using Media Server Markup Language (MSML) as definedin IETF document Saleem A., “Media Server Markup Language”, InternetDraft, draft-saleem-msml-07, Aug. 7, 2008. The media server 76 can beconfigured to perform Host Media Processing (HMP).

Other architectures or configurations for the enterprise communicationssystem 14 will be appreciated by those ordinarily skilled in the art.For example, in example embodiments the service management platform 18can be separate from the PBX 16; or the service management platform 18can include a cloud-based system.

Reference is now made to FIG. 5, which shows another embodiment of theenterprise communications system 14 with a Third Party Call Controlarchitecture. In this embodiment, the SMP 18 is a multi-layer platformthat includes a protocol layer 34, a services layer 36 and anapplication layer 38. The protocol layer 34 includes a plurality ofinterface protocols configured for enabling operation of correspondingapplications in the application layer 38. The services layer 36 includesa plurality of services that can be leveraged by the interface protocolsto create richer applications. Finally, the application layer 38includes a plurality of applications that are exposed out to thecommunication devices and that leverage corresponding ones of theservices and interface protocols for enabling the applications.

Specifically, the protocol layer 34 preferably includes protocols whichallow media to be controlled separate from data. For example, theprotocol layer 34 can include, among other things, a Session InitiationProtocol or SIP 80, a Web Services protocol 82, an ApplicationProgramming Interface or API 84, a Computer Telephony Integrationprotocol or CTI 86, and a Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions or SIMPLE protocol 88. Itis contemplated that the interface protocols 80-88 are plug-ins that caninterface directly with corresponding servers in the enterprise network20, which will be further described below.

Although SIP 80 can be utilized, it is appreciated that the system 10can operate using the above disclosed or additional protocols. As knownby those of ordinary skill in the art, SIP is the IETF (InternetEngineering Task Force) standard for multimedia session management, andmore specifically is an application-layer control protocol forestablishing, maintaining, modifying and terminating multimedia sessionsbetween two or more endpoints. As further known by those of ordinaryskill in the art, the SIP protocol 80 includes two interfaces forsignaling: SIP-Trunk (hereinafter referred to as “SIP-T”) and SIP-Line(hereinafter referred to as “SIP-L”). Specifically, the SIP-T interfaceis utilized when the endpoint is a non-specific entity or not registered(i.e., when communicating between two network entities). In contrast,the SIP-L interface is utilized when the endpoint is registered (i.e.,when dialing to a specific extension). SIP is defined in J. Rosenberg etal., “RFC 3261—Session Initiation Protocol” (June 2002), the contents ofwhich are herein incorporated by reference.

The SMP 18 also includes a plurality of enablers, among other things, aVoIP enabler 90, a Fixed Mobile Convergence or FMC enabler 92, aconference services enabler 94, a presence enabler 96 and an InstantMessaging or IM enabler 98. Each of the enablers 90-98 are used bycorresponding services in the services layer 36 that combine one or moreof the enablers. Each of the applications in the application layer 38 isthen combined with one or more of the services to perform the desiredapplication. For example, a phone call service can use the VoIP or PBXenabler, and an emergency response application can use the phone callservice, an Instant Messenger service, a video call service, an emailservice and/or a conference service.

The application layer 38 can include a conference services application63 that, together with the conference services enabler 94, enablesmultiple communication devices (including desk telephones and personalcomputers) to participate in a conference call through use of acentralized conference server 55. As seen in FIG. 5, the conferenceserver 55 is provided in the enterprise network 20 and is incommunication with the conference services enabler 94 preferably throughthe SIP protocol 80, although it is recognized that additional protocolsthat control media separate from data can be appropriate, such as theWeb Services protocol 82 or the CTI protocol 86. As will be described infurther detail below, the conference call server 55 is configured fordirecting media and data streams to and from one or more communicationdevices (i.e., mobile devices 11, telephones 17, and computers 15).

Example conference call systems and methods in accordance with exampleembodiments will now be described, referring now to FIG. 6, which showsthe system 10 when used or configured as a conference call system. Asshown, the enterprise communications platform 14 includes the conferenceserver 55 for providing conference call services for a number of clientdevices such as mobile devices 11, illustrated as one designated hostdevice 11 a and one or more participant devices 11 b, 11 c, 11 d. Themobile devices 11 can collectively form a conference call group. Thehost device 11 a is generally the mobile device 11 or associated userwho schedules and hosts a conference call session, and can, for example,be permitted to perform such hosting functions as roll call, mute all,broadcast only, conference lock, etc. In some example embodiments, theconference call session cannot commence without the presence of the hostdevice 11 a.

The enterprise communications platform 14 and the associated conferenceserver 55 can be used for generally executing conference call functions.As described above, in example embodiments, the enterprisecommunications platform 14 can include or be coupled to the media server76 (FIG. 4), wherein the enterprise communications platform 14 controlsthe media handling and media sessions of the media server 76.

Referring still to FIG. 6, in order to implement some of the conferencecall functions described herein, the enterprise communications platform14 can communicate with the mobile devices 11 by way of media sessionsand/or control sessions. Specifically, as shown in FIG. 6, the mobiledevices 11 communicate via media sessions 126 (shown as solid lines) andcontrol sessions 124 (shown as dashed lines to distinguish from themedia sessions 126). For example, the designated host device 11 acommunicates via media session 126 a and control session 124 a.Participant device 11 b communicates via media session 126 b and controlsession 124 b. Participant device 11 c communicates via media session126 c and control session 124 c. In some embodiments, as shown, theparticipant device 11 d can merely communicate via media session 126 dover the PLMN 50 (FIG. 1) or PSTN 40 (FIG. 1) only (without anassociated control session).

In some example embodiments, the media sessions 126 can be facilitatedby the enterprise communications platform 14 by way of Real-timeTransport Protocol (RTP) media sessions, and can include voice calls,video calls, circuit-switched calls or VoIP calls. In order to generateor establish a conference call session, the enterprise communicationsplatform 14 operatively connects or links at least some of the call legsof each media session 126. The particular methods and processes foroperatively connecting of media sessions 126 into a conference callsession would be understood by those skilled in the art, which can, forexample, be implemented by media shuffling or SDP (Session DescriptionProtocol) media shuffling, etc.

In some example embodiments, a data connection (e.g. the same dataconnection as used by the control sessions 124) can be further used toprovide additional data sharing between mobile devices 11. For example,during a conference call, the host mobile device 11 a can provide ortransfer a data file to the remaining mobile devices 11. Data sharingcan also include Web Services or sharing of presentation content.

In some example embodiments, during a conference call session, theenterprise communications platform 14 can receive Global PositioningSystem (GPS) information from at least some of the participant devices11, and can send the received GPS information to the devices 11, toprovide location based positioning services between the devices 11.

Reference is now made to FIG. 7 which illustrates in detail a mobiledevice 11 in which example embodiments can be applied. The mobile device11 is a two-way communication device having data and voice communicationcapabilities, and the capability to communicate with other computersystems, for example, via the Internet. Depending on the functionalityprovided by the mobile device 11, in various embodiments the mobiledevice 11 can be a handheld device, a multiple-mode communication deviceconfigured for both data and voice communication, a smartphone, a mobiletelephone or a PDA (personal digital assistant) enabled for wirelesscommunication.

The mobile device 11 includes a rigid case (not shown) housing thecomponents of the mobile device 11. The internal components of themobile device 11 can, for example, be constructed on a printed circuitboard (PCB). The description of the mobile device 11 herein mentions anumber of specific components and subsystems. Although these componentsand subsystems can be realized as discrete elements, the functions ofthe components and subsystems can also be realized by integrating,combining, or packaging one or more elements in any suitable fashion.The mobile device 11 includes a controller comprising at least oneprocessor 240 (such as a microprocessor) which controls the overalloperation of the mobile device 11. The processor 240 interacts withdevice subsystems such as a wireless communication subsystem 211 forexchanging radio frequency signals with the wireless network (e.g. WAN30 and/or PLMN 50) to perform communication functions. The processor 240interacts with additional device subsystems including a display 204 suchas a liquid crystal display (LCD) screen or any other appropriatedisplay, input devices 206 such as a keyboard and control buttons,persistent memory 244, random access memory (RAM) 246, read only memory(ROM) 248, auxiliary input/output (I/O) subsystems 250, data port 252such as a conventional serial data port or a Universal Serial Bus (USB)data port, speaker 256, microphone 258, short-range communicationsubsystem 262 (which can employ any appropriate wireless (e.g., RF),optical, or other short range communications technology), and otherdevice subsystems generally designated as 264. Some of the subsystemsshown in FIG. 2 perform communication-related functions, whereas othersubsystems can provide “resident” or on-device functions.

Display 204 can be realized as a touch-screen display in someembodiments. The touch-screen display can be constructed using atouch-sensitive input surface operatively connected to an electroniccontroller and which overlays the visible element of display 204. Thetouch-sensitive overlay and the electronic controller provide atouch-sensitive input device and the processor 240 interacts with thetouch-sensitive overlay via the electronic controller.

The wireless communication subsystem 211 includes one or morecommunication systems for communicating with wireless WAN base stations30 and wireless LAN access points 32 within the wireless network. Theparticular design of the wireless communication subsystem 211 depends onthe wireless network in which mobile device 11 is intended to operate.The mobile device 11 can send and receive communication signals over thewireless network after the required network registration or activationprocedures have been completed.

The processor 240 operates under stored program control and executessoftware modules 221 stored in memory such as persistent memory 244 orROM 248. The processor 240 can execute code means or instructions. ROM248 can contain data, program instructions or both. Persistent memory244 can contain data, program instructions or both, in some embodimentsis rewritable under control of processor 240, and can be realized usingany appropriate persistent memory technology, including EEPROM, EAROM,FLASH, and the like. As illustrated in FIG. 2, the software modules 221comprise operating system software 223 and software applications 225.

Software modules 221 or parts thereof can be temporarily loaded intovolatile memory such as the RAM 246. The RAM 246 is used for storingruntime data variables and other types of data or information, as willbe apparent to those skilled in the art. Although specific functions aredescribed for various types of memory, this is merely one example, andthose skilled in the art will appreciate that a different assignment offunctions to types of memory could also be used.

The software applications 225 can further include a range ofapplications, including, for example, an e-mail messaging application,address book, calendar application, notepad application, Internetbrowser application, voice communication (i.e., telephony) application,mapping application, or a media player application, or any combinationthereof. Each of the software applications 225 can include layoutinformation defining the placement of particular fields and graphicelements (e.g., text fields, input fields, icons, etc.) in the userinterface (i.e., the display 204) according to the application.

The modules 221 can further include a Global Positioning System (GPS)module or application which is configured for detection of ageographical position of the device 11, for example by correlatingexisting satellites. The GPS module can also receive from the enterprisecommunications platform 14 the geographical positions of the otherdevices 11.

In some embodiments, the auxiliary input/output (I/O) subsystems 250 cancomprise an external communication link or interface, for example, anEthernet connection. The auxiliary I/O subsystems 250 can furthercomprise one or more input devices, including a pointing or navigationaltool such as a clickable trackball or scroll wheel or thumbwheel, or oneor more output devices, including a mechanical transducer such as avibrator for providing vibratory notifications in response to variousevents on the mobile device 11 (e.g., receipt of an electronic messageor incoming phone call), or for other purposes such as haptic feedback(touch feedback).

In some embodiments, the mobile device 11 also includes one or moreremovable memory modules 230 (typically comprising FLASH memory) and oneor more memory module interfaces 232. Among possible functions of theremovable memory module 230 is to store information used to identify orauthenticate a user or the user's account to wireless network (e.g. WAN30 and/or PLMN 50). For example, in conjunction with certain types ofwireless networks, including GSM and successor networks, the removablememory module 230 is referred to as a Subscriber Identity Module or SIM.The memory module 230 is inserted in or operatively connected to thememory module interface 232 of the mobile device 11 in order to operatein conjunction with the wireless network.

The mobile device 11 stores data 227 in a persistent memory 244. Invarious embodiments, the data 227 includes service data comprisinginformation required by the mobile device 11 to establish and maintaincommunication with the wireless network (e.g. WAN 30 and/or PLMN 50).The data 227 can also include, for example, scheduling and connectioninformation for operatively connecting to a scheduled conference call.

The mobile device 11 also includes a battery 238 which furnishes energyfor operating the mobile device 11. The battery can be coupled to theelectrical circuitry of mobile device 11 through a battery interface236, which can manage such functions as charging the battery from anexternal power source (not shown) and the distribution of energy tovarious loads within or operatively connected to the mobile device 11.Short-range communication subsystem 262 is an additional optionalcomponent which provides for communication between the mobile device 11and different systems or devices, which need not necessarily be similardevices. For example, the short-range communication subsystem 262 caninclude an infrared device and associated circuits and components, or awireless bus protocol compliant communication mechanism such as aBLUETOOTH communication module to provide for communication withsimilarly-enabled systems and devices.

A predetermined set of applications that control basic deviceoperations, including data and possibly voice communication applicationswill normally be installed on the mobile device 11 during or aftermanufacture. Additional applications and/or upgrades to the operatingsystem software 223 or software applications 225 can also be loaded ontothe mobile device 11 through the wireless network (e.g. WAN 30 and/orPLMN 50), the auxiliary I/O subsystem 250, the data port 252, theshort-range communication subsystem 262, or other suitable subsystemsuch as 264. The downloaded programs or code modules can be permanentlyinstalled, for example, written into the program memory (e.g., thepersistent memory 244), or written into and executed from the RAM 246for execution by the processor 240 at runtime.

The mobile device 11 can provide three principal modes of communication:a data communication mode, an optional voice communication mode, and anoptional video communication mode. In the data communication mode, areceived data signal such as a text message, an e-mail message, Web pagedownload, or an image file will be processed by the wirelesscommunication subsystem 211 and input to the processor 240 for furtherprocessing. For example, a downloaded Web page can be further processedby a browser application or an e-mail message can be processed by ane-mail message messaging application and output to the display 204. Auser of the mobile device 11 can also compose data items, such as e-mailmessages, for example, using the input devices in conjunction with thedisplay 204. These composed items can be transmitted through thewireless communication subsystem 211 over the wireless network (e.g. WAN30 and/or PLMN 50). In the voice communication mode, the mobile device11 provides telephony functions and operates as a typical cellularphone. In the video communication mode, the mobile device 11 providestranscribing functions during a video conferencing session, including atleast one camera.

Reference is now made to FIG. 10, which shows a conference profileinterface 400 in accordance with a conference profiles feature, inaccordance with some example embodiments. This can be implemented by aconference call application, which can be an add-on, plug-in or app fora calendar application. Generally, in some example embodiments, theinterface 400 can be used for creating and editing conference profiles.As shown in the title bar 402 of FIG. 10, a “New Audio ConferenceProfile” can be created and stored in memory.

The profiles feature can provide meeting organizers the option to saveconference information into profiles. When creating meetings using theconference call application, the host organizers can readily populatethe conference information for the meeting by selecting a profile forthat meeting. All or some of the conference call information can beautomatically inserted into the meeting invitation. In the presentlydescribed embodiment, the profile includes an indicator to optionallyexclude sending moderator information such as the moderator access code410 to some or all of the invited participants.

Referring still to FIG. 10, the interface 400 can be used for editingconference call information of the conference call profile. As shown,the fields include Profile Name 404, Description 406, Conference Number408, Moderator Access Code 410, and Participant Access Code 412. Thesefields can be edited by the user through the interface 400.

The interface 400 also includes a checkbox 414 for selecting whether themoderator access code 410 is to be shared with attendees. The checkbox414 when deselected is used as an indicator or tag, which is stored inmemory of the device 11 a. For example, the indicator can be toggled ason or off. In other example embodiments, the moderator access code 410is masked by default, unless unchecked by the user. In otherembodiments, selection of a checkbox with suitable wording is used asthe indicator to indicate hiding or masking the moderator access code410. In some example embodiments, the indicator is automaticallygenerated by the host device 11 a. In some other example embodiments,other moderator information such as the geographic location of themoderator, is masked or excluded.

Some example embodiments can support multiple addresses, such asmultiple phone numbers and/or address links. For example, each of themultiple addresses can terminate onto the enterprise communicationsplatform 14. In some example embodiments, conference call applicationcan support a plurality of addresses for the Contact Number field whichare used to contact the enterprise communications platform 14. In someexample embodiments, once the first Conference Number 408 address field(“US Toll Free” field 416 in this example) is populated, anotherConference Number 408 field is displayed for editing. The particularlabel for the “US Toll Free” can be changed to other types of operativeconnections by selecting a menu 424.

Thus, reference is now made to FIG. 11, which shows the interface 400 ina further mode of operation. As shown in FIG. 11, the interface 400includes additional Contact Number fields, such as “Internal” 418 and“Other” 420, as shown. For example, once the US Toll Free field 416 ispopulated, the next address field appears, in this example “Internal”418. The default type of operative connection can be “US Toll Free”;thus, in some embodiments the particular type of operative connectioncan be relabeled from “US Toll Free” to “Internal” using a menu 422.Once “Internal” 418 is filled, the next address field appears, in thisexample labeled as “Other” 420. Once the “Other” 420 is filled, a newdefault field appears, shown again as a default “US Toll Free”.

Note that, in some example embodiments, the conference profile can alsosupport more than one participant access code (not shown).

Reference is now briefly made to FIG. 15, which shows a reminderinterface 1200 which is displayed at a time of a conference callsession, or a specified time beforehand. In some example embodiments,the conference call application can include a join now feature. In someexample embodiments the join now feature includes a default join option,shown as a “Join Now” button 1202, for establishing the scheduledconference call session using a default address. Once the time of thatmeeting arrives, or a predetermined time beforehand, the “Join Now”button 1202 can be displayed on the device 11 on a popup reminderinterface 1204. In example embodiments, the automatic discovery featureis used to determine whether a particular address is to be associatedwith the join now feature. When this is performed, the selection of the“Join Now” button 1202 would result in the device 11 automaticallyoperatively connecting to the enterprise communications platform 14using the identified address. The address can be a phone number andconference access code, or an address link such as an Internet address.

Referring again to FIG. 11, in some example embodiments, the “Join Now”button can be specifically assigned to a specific number or address atthis time, to be used as the default join option for the particularprofile. The host device 11 a can store a tag, represented by checkmark404, which represents the particular phone number (US Toll Free in thisexample) which is the default phone number assigned to the join nowoption (e.g. join now button 1202 (shown in FIG. 15)). The particulartag or checkmark 404 can be edited or changed to one of the otherConference Number fields through the interface 400.

Reference is now made to FIG. 9, which shows an example user interface300 displayed on the display 204 for scheduling a conference call, inaccordance with an example embodiment. In the example embodiment shown,the user interface 300 is for example implemented by a conference callapplication (as a stand-alone or in combination with other applications)resident on the host device 11 a, which can be an add-on, plug-in or appfor a calendar application. The user interface 300 can form part of aconference call session scheduling process.

Still referring to FIG. 9, the user interface 300 can be edited toschedule a conference call session having a subject and which is tooccur at a scheduled time and date. For example, the time and date ofthe scheduled conference call session can be stored within theconference call application or a calendar application. For example, thescheduled conference call has a subject field of “PM-PO-UX Synch.” andhas a scheduled date field of “May 8, 2009 at 3:30 PM-4:00 PM”. The userinterface 300 can be manually triggered by launching and subsequentlyoperating the conference call application.

As shown in FIG. 9, the user interface 300 also includes an options menu306 to perform functions such as editing the existing scheduledconference call, scheduling new conference calls, and inviting newparticipants. During the conference call scheduling process, theconference call scheduling information is sent from the host device 11 ato the enterprise communications platform 14, which stores theinformation in a memory. In some example embodiments, the host mobiledevice 11 a sends an invitation message directly or indirectly to therecipient invitee client devices 11. In some example embodiments, thehost mobile device 11 a receives a response to the invitation messagedirectly or indirectly from the invitee client devices 11. The hostmobile device 11 a can update the enterprise communications platform 14in such example embodiments.

At the time of the scheduled conference call, or a specified timebeforehand, the enterprise communications platform 14 can contact eachof the devices 11 to join the media sessions together. In exampleembodiments, the devices 11 can also dial or link into the enterprisecommunications platform 14 using dialing or address link informationreceived during scheduling.

As shown in FIG. 9, the user interface 300 includes a title bar 302, astatus icon 304, an options menu 306, and participant icons 310 a-310 d(each or individually 310) which display the status of each participantfor the conference call. The participant icons 310 can, for example, bea photo or avatar of the individual user. A cursor 312 is also shown forindicating which item(s) on the user interface 300 are to be selected(e.g., controllable by a user input device such as a touchscreen, touchscrollball or mouse). The status icon 304 displays the present status ofthe conference call, for example “Scheduled CC” (Conference Call) asshown.

Referring now to the participant icons 310, in the example shown, theuser interface 300 is displayed on the host device 11 a, indicated as“You-Host” as shown in icon 310 a. The participant icon 310 b associatedwith “John” is indicated as “Declined”. The participant icon 310 bassociated with “Sally” is indicated as “Tentative”. The participanticon 310 d associated with “Kevin” is indicated as “Accepted.” Contactinformation such as e-mail address or phone number for the participantscan be pre-stored in association with the participant names (or can bemanually entered, as appropriate). The status of each participant icon310 can also be shown, for example, as Accepted, Tentative, or Declined.

As shown in FIG. 9, in some example embodiments the host device 11 a canalso select a menu 314 to designate the scheduled conference call as a“closed” conference call. In a “closed” call, only the specified oreligible participant devices 11 designated by the host device 11 a canjoin the call. Additionally, for example, only a specified number ofparticipants can join the call. In some example embodiments, in a“closed” call further authentication of those participant devices 11 canbe performed when attempting to access the scheduled conference call. Asshown, the host device I la also has the option to use the menu 314 toset the scheduled conference call as an “open” conference call, whereinany participant device 11 (designated as eligible or not) can join.

As shown, the Connection fields 316 include various addresses foroperatively connecting to the enterprise communications platform 14. Insome example embodiments, the Connection fields 316 can be populatedfrom a profile with one or more phone numbers, and moderator orparticipant access codes, for operatively connecting to the enterprisecommunications platform 14. In the example shown, the phone numbersshown are USA Toll Free 416, Internal extension 418, and Other 420.Additional addresses can also be populated within the Connection fields316, such as an Internet, Intranet, or SIP address link (not shown).Some of the information in the Connection fields graphical userinterface 316 can be auto-populated with address information retrievedfrom a conference profile stored in memory. The moderator access code410 and the participant access code 412 can also be contained in theConnection fields 316.

Reference is now made to FIG. 12A, which shows an interface 500 inaccordance with an example embodiment. In some example embodiments, theinterface 500 is displayed as a consequence of selection of the optionsmenu 306 (or a sub-menu thereof) from FIG. 9.

As illustrated in the interface 500, the saved conference profile can beaccessed to populate at least some of the conference call schedulingfields. For example, a desired profile can be selected from a ConferenceProfile option or Conference Profile drop-down menu 508. Once selected,at least some of the address fields and the access codes can beautomatically populated. As shown, at least some of the US Toll Free416, Internal 418, Other 420, moderator access code 410, and participantaccess code 412 are automatically retrieved and copied into respectivefields. These fields can be further edited by the user through theinterface 500. Accordingly, the profile can be used as a starting pointfor scheduling a conference call in some example embodiments.

In some example embodiments, the host device 11 a can also store a tag,represented by checkmark 502, which represents the particular phonenumber (US Toll Free 416 in this example) which is the default phonenumber assigned to the join now option (e.g. join now button 1202 (shownin FIG. 15)). Through the interface 500, the user can edit or selectwhich address or phone number is to be used for the join now option.

Thus, reference is made to FIGS. 12B and 12C, which illustrate how theinterface 500 can be used to select a different phone number, forexample Internal 418, as the default phone number assigned to the joinnow option. As shown in FIGS. 12A and 12B, a drop-down menu 504 forInternal 418 is selected, and the “Use for Join Now” option 506 can beselected. As shown in FIG. 12C, the tag, represented by checkmark 502,is now assigned to the Internal 418 phone number.

in further example embodiments, a tag is saved or flagged within theConnection fields 316 (shown in FIG. 9), for example using an XML tag orother indicator.

Referring again to FIG. 10, as indicated above, an identifier for theparticular profile can be saved such that the host device 11 a can sendan invitation message for the conference call, excluding the moderatoraccess code 410. For the following example, it is presumed that anidentifier for excluding sending of the moderator access code 410 toinvited participants is saved for this particular profile and session.Thus, the host device 11 a sends an invitation message to an invitedparticipant device in relation to the scheduled conference call, whereinthe message includes the address information and the participant accesscode 412 but excludes the moderator access code 410. The identifier forthis exclusion is checked and verified prior to sending.

Accordingly, reference is now made to FIG. 13, which shows a userinterface 600 for displaying a received invitation message 602 on anon-host participant device 11. The device 11 first receives theinvitation message 602 from another communication device, such as hostdevice 11 a, with respect to a scheduled conference call. As shown, themessage 602 as displayed can include a number of fields 604 which relateto conference call scheduling information. The fields 604 includeSubject, Start time, End time, Recurrence, Host/Organizer, andConnection 620. The Connection 620 can include sub-fields containing aplurality of connection addresses for operatively connecting to theenterprise communications platform 14, such as web information or audio(dialing) information (not shown) and participant access code 702 foraccessing the conference call. The moderator access code is not presentas it was not received by the device 11. In some example embodiments,the example user interface 600 can be displayed using a calendarapplication or a conference calling add-on, plug-in or app, as astand-alone or in combination with other applications. The userinterface 600 can also form part of the conference call sessionscheduling process.

In some example embodiments, the invitation message 602 can be receivedas an e-mail message designating the participant's e-mail address, butcan also be in other forms such as short message service (SMS), SIPmessage, instant messaging, or calendar invite. The message 602 can bereceived directly or indirectly from a host device 11 a.

As shown on the interface 600, a number of response options 606 can beselected in order to respond to the invitation message 602. As shown,the response options 606 include Accept 610, Decline 612, Tentative 614,or Forward 616. Upon selection of one or more of the response options606, a communication containing the response is sent to the host device11 a. In further example embodiments, selection of the Accept 610 optioncan result in the details of the invitation message 602 being stored asa calendar event record in a calendar application of the device 11. TheForward 616 option can be used to forward the invitation message to anew participant client device.

Reference is now made to FIG. 14, which shows an example interface 700for editing the received invitation message. As shown in the interface700, the moderator access code or field is absent as no moderator accesscode was received from the host device 11 a. The participant access code702 is displayed and stored, and can be used by the device to access theconference call when contacting the enterprise communications platform14.

Through the interface 700, invited users can select from a list whichphone number or address they would like to use for the join now button1202 (shown in FIG. 15). At the time of the scheduled conference call,or a specified time beforehand, the devices 11 can display the reminderinterface 1200 including the join now button 1202 (shown in FIG. 15), todial or link into the enterprise communications platform 14.

In some example embodiments, the interface 700 can now be used by thenon-host participant device 11 to save the particular profile, eitherautomatically or manually. This profile can be saved for future use andretrieval of the fields, for example the particular address andparticipant access code information. For example, the user can schedulea future conference call with the same address and participant accesscode information.

Referring again to the interface 600 of FIG. 13, if web information isreceived, an address link (not shown) can be selected as the defaultjoin option for joining the conference call session. If the conferencecall is a closed call, the enterprise communications platform 14 canthen authenticate the device 11, for example by authenticating anidentifier of the device 11 (in one embodiment, using a particularpersistent device identifier). Upon authentication, a conference callsession can be established between the device 11 and the enterprisecommunications platform 14, which can include a media session 126 (shownin FIG. 6).

As can be appreciated, in some example embodiments the address link canidentify the enterprise communications platform 14 as well as thescheduled conference call session and/or the participant identifier, andcan include a Uniform Resource Locator (URL), a Uniform ResourceIdentifier (URI), or other suitable address.

Reference is now made to FIG. 8, which shows an example flow diagram ofa method 800 for protecting moderator access in accordance with anexample embodiment. At step 802, an interface is displayed for theinterface can be used for receiving user input for creating a newconference call profile, or editing an existing conference call profile.The user can edit conference call scheduling information, such asediting one or more addressees for communicating with a conference callserver. The user can also edit a moderator access code and a participantaccess code. At step 806, the device can generate an indicator for theconference call profile for excluding sending of moderator information,such as the moderator access code, to invited participants. This can bebased on user input, for example by selecting or deselecting a checkbox.At step 810, the conference call profile is stored in memory, along withthe indicator.

The user can then wish to create or schedule a new conference call.Thus, at step 812, the device displays a conference call schedulinginterface for scheduling a conference call. At step 814, the deviceretrieves the conference call profile from the memory. This can be basedon the user selecting a desired conference call profile. At step 816,the device populates the conference call scheduling interface with atleast some of the stored profile. The user can further edit thescheduled conference call through the conference call schedulinginterface. At step 818, a send instruction is received, for example byuser input through the conference call scheduling interface. At step820, the device verifies whether the indicator states that the moderatoraccess code is to be excluded. At step 822, the device accordingly sendsan invitation message to the invited participants in relation to thescheduled conference call. The invitation message includes theparticipant access code and excludes the moderator access code.

In some example embodiments, at least some of the method 800 can beperformed by a host device 11 a or a non-host participant device 11,depending on the particular application. For example, referring again tostep 802, the interface for editing the profile can be populated by thedevice at least partially based upon an existing conference call eventrecord, such as one that was previously created, received, or sent bythe device. This allows an existing record to be the basis or startingpoint for a new profile.

It can be appreciated that, in some example embodiments, the moderatoraccess code need not be limited to a dialed passcode, but can be acomputer-based password or key (encryption or signature) when accessingthe address link.

It can be appreciated that some example embodiments can be used toexclude or mask other moderator information, such as the moderator'spresent or anticipated location.

It can be appreciated that the specific words as shown in the varioususer interfaces are intended to be illustrative only. For example, anysuitable words or phrases can be used, and would not be limited to theEnglish language. For example, any number of multi-lingual variations indifferent languages can be displayed or output from the device.

Variations of the above example systems and methods can be used. Whilesome of the above examples have been described as occurring in aparticular order, it will be appreciated to persons skilled in the artthat some of the messages or steps or processes can be performed in adifferent order provided that the result of the changed order of anygiven step will not prevent or impair the occurrence of subsequentsteps. Furthermore, some of the messages or steps described above can beremoved or combined in other embodiments, and some of the messages orsteps described above can be separated into a number of sub-messages orsub-steps in other embodiments. Even further, some or all of the stepsof the conversations can be repeated, as necessary. Elements describedas methods or steps similarly apply to systems or subcomponents, andvice-versa. Reference to such words as “sending” or “receiving” could beinterchanged depending on the perspective of the particular device.

Variations can be made to some example embodiments, which can includecombinations and sub-combinations of any of the above. The variousembodiments presented above are merely examples and are in no way meantto limit the scope of this disclosure. Variations of the innovationsdescribed herein will be apparent to persons of ordinary skill in theart having the benefit of the present disclosure, such variations beingwithin the intended scope of the present disclosure. In particular,features from one or more of the above-described embodiments can beselected to create alternative embodiments comprised of asub-combination of features which might not have been explicitlydescribed above. In addition, features from one or more of theabove-described embodiments can be selected and combined to createalternative embodiments comprised of a combination of features whichmight not have been explicitly described above. Features suitable forsuch combinations and sub-combinations would be readily apparent topersons skilled in the art upon review of the present disclosure as awhole. The subject matter described herein intends to cover and embraceall suitable changes in technology.

What is claimed is:
 1. A method for protecting moderator access using acommunication device, the method comprising: displaying an interface forediting a conference call profile, the conference call profile includingconference call scheduling information including one or more addressesfor communicating with a conference call server, wherein the conferencecall scheduling information further includes a moderator access code anda participant access code; generating an indicator for the conferencecall profile for excluding sending of the moderator access code toinvited participants; storing the conference call profile including theindicator in a memory of the communication device; and sending a messageto the invited participants in relation to a conference call scheduledusing the stored conference call profile, the message including theparticipant access code and excluding the moderator access code if theindicator indicates excluding the moderator access code.
 2. The methodas claimed in claim 1, further comprising displaying a selectable optionon the interface to exclude sending the moderator access code to invitedparticipants.
 3. The method as claimed in claim 2, wherein thegenerating of the indicator is in response to selection or deselectionof the option.
 4. The method as claimed in claim 2, wherein theselectable option includes a checkbox.
 5. The method as claimed in claim1, further comprising: displaying a conference call scheduling interfacefor scheduling a conference call.
 6. The method as claimed in claim 5,wherein the conference call scheduling interface is configurable foridentifying the invited participants.
 7. The method as claimed in claim5, further comprising: verifying the indicator prior to sending.
 8. Themethod as claimed in claim 1, wherein the indicator includes a tag. 9.The method as claimed in claim 1, wherein the one or more addressesincludes at least a phone number or an Internet address.
 10. Acommunication device comprising: a controller; a communicationssubsystem; a memory; and a display for displaying an interface forediting a conference call profile, the conference call profile includingconference call scheduling information including one or more addressesfor communicating with a conference call server, wherein the conferencecall scheduling information further includes a moderator access code anda participant access code, wherein the controller is configured for:generating an indicator for the conference call profile for excludingsending of the moderator access code to invited participants, storingthe conference call profile including the indicator in the memory; andsending a message to the invited participants in relation to aconference call scheduled using the stored conference call profile, themessage including the participant access code and excluding themoderator access code if the indicator indicates excluding the moderatoraccess code.
 11. The communication device as claimed in claim 10,wherein the interface further includes a selectable option to excludesending the moderator access code to invited participants.
 12. Thecommunication device as claimed in claim 11, wherein the generating ofthe indicator is in response to selection or deselection of the option.13. The communication device as claimed in claim 11, wherein theselectable option includes a checkbox.
 14. The communication device asclaimed in claim 10, wherein the controller is further configured for:displaying a conference call scheduling interface for scheduling aconference call.
 15. The communication device as claimed in claim 14,wherein the conference call scheduling interface is configurable foridentifying the invited participants.
 16. The communication device asclaimed in claim 14, wherein the controller is further configured for:verifying the indicator prior to sending.
 17. The communication deviceas claimed in claim 10, wherein the indicator includes a tag.
 18. Thecommunication device as claimed in claim 10, wherein the one or moreaddresses includes at least a phone number or an Internet address.
 19. Anon-transitory computer readable medium having stored instructions that,when executed by a communication device, cause the communication deviceto perform a method for protecting moderator access using thecommunication device, the method comprising: displaying an interface forediting a conference call profile, the conference call profile includingconference call scheduling information including one or more addressesfor communicating with a conference call server, wherein the conferencecall scheduling information further includes a moderator access code anda participant access code; generating an indicator for the conferencecall profile for excluding sending of the moderator access code toinvited participants; storing the conference call profile including theindicator in a memory of the communication device; sending a message tothe invited participants in relation to a conference call scheduledusing the stored conference call profile, the message including theparticipant access code and excluding the moderator access code if theindicator indicates excluding the moderator access code.
 20. Thecomputer readable medium as claimed in claim 19, wherein the methodfurther comprising displaying a selectable option on the interface toexclude sending the moderator access code to invited participants. 21.The computer readable medium as claimed in claim 20, wherein thegenerating of the indicator is in response to selection or deselectionof the option.
 22. The computer readable medium as claimed in claim 20,wherein the selectable option includes a checkbox.
 23. The computerreadable medium as claimed in claim 19, wherein the method furthercomprising: displaying a conference call scheduling interface forscheduling a conference call.
 24. The computer readable medium asclaimed in claim 23, wherein the conference call scheduling interface isconfigurable for identifying the invited participants.
 25. The computerreadable medium as claimed in claim 23, wherein the method furthercomprising: verifying the indicator prior to sending.
 26. The computerreadable medium as claimed in claim 19, wherein the indicator includes atag.
 27. The computer readable medium as claimed in claim 19, whereinthe one or more addresses includes at least a phone number or anInternet address.